Skip to main content

Description of configuration variables

Source

This is more of a description than a tutorial. Here you will find information about the configuration variables that must be provided for history tools to work.

Back to Readme

Basic Variables

NameTypeDescriptionDefault
BLOCKCHAIN_ENDPOINTstringBlockchain API addresnone
BLOCKCHAIN_CHAIN_IDstringBlockchain ID stringnone
HYPERION_URLstringHyperion API urlnone
BLOCK_READER_ENDPOINTSstringComma separated list of State History Plugin WS pathsnone
BLOCK_READER_FETCH_BLOCKnumberNumber (0/1) value that specifies whether to fetch the signed block data1
BLOCK_READER_FETCH_DELTASnumberNumber (0/1) value that specifies whether to fetch deltas1
BLOCK_READER_FETCH_TRACESnumberNumber (0/1) value that specifies whether to fetch traces1
READER_MAX_THREADSnumberspecify the maximum number of threads dedicated to the reader process1
FILTER_MAX_THREADSnumberspecify the maximum number of threads dedicated to the reader process1
PROCESSOR_MAX_THREADSnumberspecify the maximum number of threads dedicated to the reader process1
API_PORTnumberHistory Tools API port numbernone
BROADCAST_PORTnumberBroadcast port numbernone
BROADCAST_HOSTstringBroadcast hostnone
MONGO_HOSTSstringComma separated list of database hostsnone
MONGO_PORTSstringComma separated list of database portsnone
MONGO_DB_NAMEstringName of the databasenone
MONGO_USERstringDatabase usernone
MONGO_PASSWORDstringDatabase user passwordnone
MODEstringHistory Tools run mode label "default"/"replay""default"
SCANNER_SCAN_KEYstringLabel for scanned blocks in replay mode. It serves the main purpose of separating and keeping in the database logs the history of which blocks were scanned for what purpose. It may happen that blocks in the same instance will have to be downloaded again, for this you need to enter a new label.none
START_BLOCKnumberBeginning of block scanning in replay mode.none
END_BLOCKnumberEnd of block scan in replay mode.none

Advanced Variables

The following settings are additional for more advanced users who want to tweak the work of the tools to use more available resources

NameTypeDescriptionDefault
SCANNER_NODES_MAX_CHUNK_SIZEnumberSpecifies the number of blocks in a subset of the block range. Modifying this value may affect the scanning speed, more smaller subsets will speed up the process in case of multi-threaded or multiple reader instances.100
ABIS_SERVICE_LIMITnumber"setabi" action fetch limit100
ABIS_SERVICE_FILTERstring"setabi" action filter"eosio:setabi"
READER_INVIOLABLE_THREADS_COUNTnumberThe number of threads that cannot be allocated to the reader process.0
PROCESSOR_INVIOLABLE_THREADS_COUNTnumberThe number of threads that cannot be allocated to the processor process.0
FILTER_INVIOLABLE_THREADS_COUNTnumberThe number of threads that cannot be allocated to the filter process.0
START_FROM_HEADnumberSpecifies (1 = true/ 0 = false) whether reading a blocks should start with the head or the last irreversible block number.0
UNPROCESSED_BLOCK_QUEUE_MAX_BYTES_SIZEnumberThe maximum size of the queue in bytes.256000000
UNPROCESSED_BLOCK_QUEUE_SIZE_CHECK_INTERVALnumberSpecifies the waiting time in milliseconds to check that the current queue size in bytes does not exceed the maximum allowed.2000
UNPROCESSED_BLOCK_QUEUE_BATCH_SIZEnumberBatch size of unprocessed blocks sent to the database at one time. The batch setting can be modified to optimize the transfer consumption to the database.100
PROCESSOR_TASK_QUEUE_CHECK_INTERVALnumberTime to wait in milliseconds to check if there are new processor tasks available. This option is needed when the filter finishes its work and will not send information about the update to the processor.5000